Realtime triggering framework

ABSTRACT

A computer-implemented method generates a trigger registration for a selected triggering type. The generated trigger registration is stored in a triggering persistency. A received event from an event persistency is analyzed and data associated with the analyzed event is compared with the triggering persistency. Based on the comparison and using a pattern execution framework, an enterprise threat detection (ETD) pattern is processed to perform actions responsive to the received event.

CLAIM OF PRIORITY

This application claims priority under 35 USC § 120 to U.S. patent application Ser. No. 15/216,201, filed on Jul. 21, 2016 titled “REALTIME TRIGGERING FRAMEWORK” (Attorney Docket No.: 22135-0953001); the entire contents of which are hereby incorporated by reference.

BACKGROUND

Enterprise threat detection (ETD) typically allows analyzing log data from various enterprise computing systems over known ETD patterns indicating threats to the computing systems. Currently the ETD patterns are processed on a periodic basis, for example, every ten minutes. For this example timeframe, it can take up to ten minutes before a threat can be detected using the EDT pattern; potentially allowing data theft, damage, etc. (including possibly to the ETD system itself) to occur within the enterprise computing system until the threat detection system processes log data against the ETD patterns at the next period threshold. However, increasing the period frequency (for example, to process an ETD pattern every minute or more frequently), raises computational and resource loads on one or more computers due to the increased frequency of processing. As some types of enterprise computing system attacks occur very infrequently (for example, less than once per month), an approach to increase the period frequency is in conflict with a goal to decrease computer operation costs.

SUMMARY

The present disclosure describes methods and systems, including computer-implemented methods, computer program products, and computer systems for realtime enterprise threat detection (ETD).

In an implementation, a computer-implemented method generates a trigger registration for a selected triggering type. The generated trigger registration is stored in a triggering persistency. A received event from an event persistency is analyzed and data associated with the analyzed event is compared with the triggering persistency. Based on the comparison and using a pattern execution framework, an enterprise threat detection (ETD) pattern is processed to perform actions responsive to the received event.

The above-described implementation is implementable using a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system comprising a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method/the instructions stored on the non-transitory, computer-readable medium.

The subject matter described in this specification can be implemented in particular implementations so as to realize one or more of the following advantages. First, execution occurs in realtime or in substantially realtime. Immediately after a log entry arrives in an event persistency, an alert can be detected and reported if applicable to the log entry. Second, execution of an ETD pattern can be on demand. With triggered ETD patterns there are no unneeded scheduled ETD pattern executions that results in negative findings. This saves computing (hardware and software) resources. Third, ETD patterns are executed in parallel with processing threads. Different ETD patterns triggered through the same log entry/entries are executed at the same time. This allows a potential threat to be reported sooner than running each ETD pattern sequentially. In sequential execution some delays would occur. Fourth, complex and expensive ETD patterns can be divided into a chain of simple ETD patterns. This division can reduce complexity and allows a chain to be broken if one of the chained ETD patterns results in no findings. Fifth, at some point in the execution of an ETD pattern chain, a fork (for example, calling several ETD patterns simultaneously) can be performed. This forking permits faster execution and receipt of ETD pattern execution results. Other advantages will be apparent to those of ordinary skill in the art.

The details of one or more implementations of the subject matter of this specification are set forth in the accompanying drawings and the description below. Other features, aspects, and advantages of the subject matter will become apparent from the description, the drawings, and the claims.

DESCRIPTION OF DRAWINGS

FIG. 1 is a block diagram illustrating data/process flow for a realtime enterprise threat detection (ETD) triggering framework, according to an implementation.

FIG. 2 is a flow chart illustrating trigger creation activity for the realtime ETD triggering framework, according to an implementation.

FIG. 3 is a block diagram illustrating additional detail of the dispatcher of the realtime ETD triggering framework, according to an implementation.

FIGS. 4A and 4B illustrate a flowchart of an example method for realtime ETD threat detection, according to an implementation.

FIG. 5 is a block diagram of an exemplary computer system used to provide computational functionalities associated with described algorithms, methods, functions, processes, flows, and procedures as described in the instant disclosure, according to an implementation.

Like reference numbers and designations in the various drawings indicate like elements.

DETAILED DESCRIPTION

The following detailed description describes a realtime triggering framework for realtime enterprise threat detection (ETD), and is presented to enable any person skilled in the art to make and use the disclosed subject matter in the context of one or more particular implementations. Various modifications to the disclosed implementations will be readily apparent to those skilled in the art, and the general principles defined herein may be applied to other implementations and applications without departing from scope of the disclosure. Thus, the present disclosure is not intended to be limited to the described or illustrated implementations, but is to be accorded the widest scope consistent with the principles and features disclosed herein.

For the purposes of this disclosure, the term “real-time,” “real time,” “realtime,” “real (fast) time (RFT),” “near(ly) real-time (NRT),” “quasi real-time,” or similar terms (as understood by one of ordinary skill in the art) means that an action and a response are temporally proximate such that an individual perceives the action and the response occurring substantially simultaneously. For example, the time difference for a response to display (or for an initiation of a display) of data following the individual's action to access the data may be less than 1 ms, less than 1 sec., less than 5 secs., etc. While the requested data need not be displayed (or initiated for display) instantaneously, it is displayed (or initiated for display) without any intentional delay, taking into account processing limitations of a described computing system and time required to, for example, gather, accurately measure, analyze, process, store, and/or transmit the data.

ETD typically allows analyzing data (for example, log data) from various enterprise computing systems over known ETD patterns indicating threats to the computing systems. While the following description focused on the use of log data for analysis, other types of data associated with ETD computing systems can also be leveraged for ETD analysis using the described methodology. Currently ETD patterns are processed on a periodic basis, for example, every ten minutes. For this example timeframe, it can take up to ten minutes before a threat can be detected from analysis of entries in log files using one or more ETD patterns. This delay can potentially allow data theft, damage, etc. (including possibly to the ETD system itself which would further compromise ETD) to occur within the enterprise computing system until the threat detection system processes log data against particular ETD patterns at the next processing period threshold. However, increasing the processing period frequency (for example, to process an ETD pattern every minute or more frequently) to mitigate this concern, raises computational and resource loads on one or more computers due to the increased frequency of processing. As some types of enterprise computing system attacks occur very infrequently (for example, less than once per month), an approach to increase the period frequency is in direct conflict with a goal to decrease computer operation costs.

The disclosure describes a solution framework where an ETD pattern is executed on-demand. For purposes of this disclosure, “on-demand” means that ETD pattern execution is triggered as soon as content has arrived in a log file that is related to the ETD pattern or a particular event has occurred. For example, in an ETD pattern detection, a log file entry having a particular value in one of the fields is written to a log or an alert is raised by the processing of another ETD pattern (event detection) which triggers a subsequent ETD pattern(s) to execute. As a further example, a log entry could include the assignment of a particular role (for example, a supervisory or an administrative role) to a user. The assignment of the particular role could, for example, have been detected using a first ETD pattern and can trigger the use of a second ETD pattern used to detect the criticality of this role assignment (for example: 1) who is the particular user?; 2) identification of which user assigned the particular role?; and 3) what actions has the user been performing since the particular role was assigned?). If the role assignment is determined to have been critical (for example, the user himself/herself assigned the new role to themselves, the user has accessed a high-security database in the enterprise computing system, etc.), the second ETD pattern can initiate generation of an alert (for example, executing additional computer code, processes, etc. to generate an alert or notifying the first ETD pattern to initiate generation of an alert, locking down particular enterprise computing systems, temporarily suspending the role assignment, etc.).

FIG. 1 is a block diagram illustrating an example data/process flow for a realtime enterprise threat detection (ETD) triggering framework 100, according to an implementation. The data/process flow contains a forensic lab: pattern facet 102, trigger persistency 104, dispatcher 106, event persistency 108, processing thread(s) 110 (hereinafter “threads”), pattern execution framework 112, and alert detection 114. As will be appreciated by those of ordinary skill in the art, the example data/process flow is one possible arrangement of components and data/process flow. Other components and data/process flows consistent with this disclosure are possible and are considered to be within the scope of this disclosure.

In addition to the ETD scheduled triggering pattern “Periodically” (as described above), a new ETD pattern execution mode called “Trigger” is introduced. The trigger mode allows an ETD pattern to be executed “By Event” or “By Pattern.”

FIG. 2 is a flow chart illustrating trigger creation activity 200 for the realtime ETD triggering framework, according to an implementation. For clarity of presentation, the description that follows generally describes method 200 in the context of the other figures in this description. However, it will be understood that method 200 may be performed, for example, by any suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware as appropriate. In some implementations, various steps of method 200 can be run in parallel, in combination, in loops, or in any order.

At 202, an ETD triggering configuration application (for example a forensic lab configuration application—not illustrated) that is associated with the forensic lab: pattern facet 102 is used by an ETD pattern designer to configure a triggering mode (for example, either “Periodically” or “Trigger”) and associated trigger(s). In the case of triggering mode “Trigger,” a selection can then be made of “By Event” or “By Pattern.” From 202, method 200 proceeds to 204.

At 204, for a configured trigger (either by event or by pattern), a trigger registration (for example, an entry in the example table “Trigger” below) is generated and added to a registration list (not illustrated) stored in the trigger persistency 104.

The trigger persistency 104 is typically a database (for example, either a conventional or in-memory database) used to store the registration list of trigger registrations. In other implementations, the trigger persistency 104 can use any type of data storage and data structure consistent with this disclosure. In one particular implementation, a trigger entry (each entry in the entity Trigger corresponds to one registration) could be defined similarly to:

entity Trigger { key PatternId : Binary(16); key TriggerName : String(5000); key TriggerType : String(5000); ChangeTimestamp : UTCTimestamp; Namespace : String(500); }; where TriggerName is either a PatternId of the triggering ETD pattern (in case of triggering by Pattern) or a SemanticEventId (in case of triggering by Event). From 204, method 200 stops.

Returning to FIG. 1, a dispatcher 106 (see below), whose response time is relatively significant in the ETD triggering framework 100, has only read to the trigger persistency 104. For example, read access in an in-memory database is extremely fast. Write accesses to the trigger persistency 104 are performed during ETD pattern design time where high performance is not a significant factor.

In the example of a selected “By Event” trigger, one or more values of a semantic event are set (registered content), which are used as trigger content, and an ETD pattern name (registered ETD pattern) identified to execute if the trigger is activated. If the semantic event contains a registered value, the trigger is activated and the registered ETD pattern is executed.

In the example of a selected “By Pattern” trigger, the registration list typically contains content relevant for ETD pattern triggering (registered content) and an identified ETD pattern name to execute (registered ETD pattern). With the registered content and the registered ETD pattern, the registration list can be used to quickly and efficiently check whether registered content has been detected. If the registered content is detected. If the registered content is detected, the registered ETD pattern is executed.

For example, if example registrations (entries in entity Trigger) resemble:

PatternId TriggerName TriggerType ChangeTimestamp Namespace A X ByPattern . . . . . . A Y ByPattern . . . . . . After execution of pattern X, pattern A is executed if the execution of pattern X results in an Alert. The same is also true for pattern Y, that is, if after execution of pattern Y, any alerts occur, then the pattern A is called.

In the example of a selected “By Events” trigger, the example registration could resemble:

PatternId TriggerName TriggerType ChangeTimestamp Namespace A SemEventNameB ByEvent . . . . . . A SemEventNameC ByEvent . . . . . . In this case the Dispatcher (more precisely, the “By Event” Trigger Manager 304—see FIG. 3) checks in the events persistency 108 if logs with Entries corresponding to SemEventNameB and SemEventNameC arrived. If so, then pattern A is called. Technical implementations are typically efficient enough to allow fast execution (for example, every second) to check if any log entries arrived that correspond to TriggerNames.

ETD patterns are data objects saved in JSON format in our pattern persistency. ETD patterns contain paths. Each path contains subsets, which represent WHERE conditions (for example “filter only systems A, B, and C” or “do not consider IP addresses starting with “0.10,” etc.). Paths can be connected over references (which are represented by JOINS). Each pattern is translated into an SQL query, meaning that a pattern execution is a SQL query execution. Alerts are pattern results or query execution results.

After execution of an ETD pattern (any type of ETD pattern—scheduled or triggered) and if the executed ETD pattern results in an alert(s), the pattern execution framework 112 calls the dispatcher 106 and passes the PatternId of the executed ETD pattern. Dispatcher 106 checks in the trigger persistency 104 for registrations for the received PatternId (for example, using field “TriggerName”) with a triggering type of “By Pattern” (for example, using field “TriggerType”). If YES, then corresponding ETD patterns are executed in parallel using different threads 110.

The dispatcher 106 is a computational daemon thread or a job executing at a high frequency (for example, every 1 sec.). The dispatcher 106 accesses and analyzes one or more events in the event persistency (for example, arriving log entries) and determines, using the registration list stored in the trigger persistency 104, whether arriving content in one or more events has been associated with a trigger (whether by event or by pattern). Given the dispatcher 106's computational speed, the system is considered to run in realtime or in substantially realtime. If a determination is made that such content has arrived, corresponding ETD patterns are selected for processing and threads 110 established for processing the corresponding ETD patterns. With this methodology, execution of an ETD pattern is “on demand,” meaning when corresponding event data demands that an ETD pattern be triggered to be executed. With triggered ETD patterns there are no unneeded scheduled ETD pattern executions that result in negative findings. This saves computing (hardware and software) resources.

Each of the selected ETD patterns is processed in a separate thread 110 to permit parallelization of ETD responses. Different ETD patterns triggered through the same log entry/entries are executed at the same time in parallel. This allows a potential threat to be reported more quickly than running through ETD patterns in some sequential order.

Dispatcher 106 reads “By Events” registrations from the trigger persistency 104. Each registration, in addition to a PatternId, contains a SemanticEventId. In the event persistency 108, there is a corresponding field containing a SemanticEvent. The dispatcher 106 determines (for example, every 1 second) if, for the SemanticEventIds, any events containing a corresponding SemanticEvent arrived in the event persistency 108. If the determination is TRUE, a list of such registrations is created. For each of these registrations, a thread 110 is allocated by the dispatcher 106 that processes an ETD pattern. Each thread 110 typically processes one ETD pattern one time and is stops following the processing to free any used computational resources (hardware and software).

A persistency call (triggering and event) is typically performed in one query call for efficiency. Analysis is strictly based on triggering persistency 104 registrations.

In typical implementations, a latest insertion timestamp of read events (from the event persistency 108) is persisted (for example, in a database, memory storage, etc.), so that the next reading from the event persistency 108 (for example, 1 second later) picks up immediately after the stored timestamp.

The event persistency 108 is typically a database (for example, either a conventional or in-memory database) used to store log data for an enterprise computing system. In other implementations, the event persistency 108 can use any type of data storage and data structure consistent with this disclosure. In some implementations, the event persistency 108 can be used to persist a subset of log data for an enterprise computing system (for example, only data applicable to certain defined periodic or trigger triggering while other enterprise computing system data can be stored in a different data store for analysis). This subset configuration might allow for faster processing of particular data, while the dispatcher 106 processed data for the remaining data using other data stores acting as additional event persistencies 108. In some implementations, more than one dispatcher 106 could be configured to execute in different threads/jobs to permit parallelization of the dispatcher for increased performance. In these implementations, the multiple dispatchers 106 can be configured to communicate with each other regarding, for example, status, triggered triggers, ETD pattern execution status, metrics, results, etc.

In a typical implementation, events are stored in a column table in the event persistency 108. This table is typically partitioned on a daily basis, so that, for example, up to 2 billion entries can be stored daily. Since the dispatcher 106's reading access time for the event persistency 108 is very short (for example, 1 second), the response time to evaluate if any ETD patterns should be triggered typically takes approximately 2 ms, which permits realtime ETD pattern triggering.

In a typical implementation, an example structure of the event persistency (field “TechnicalLogEntryType contains mentioned SemanticEvent that corresponds to SemanticEventId saved in field TriggerName in the trigger persistency 104):

entity Events { Id : UUID; Timestamp : UTCTimestamp; TechnicalGroupId : UUID; TechnicalLogEntryType : ShortString; TechnicalNumber : Integer64; TechnicalNumberRange : ShortString; TechnicalTimestampOfInsertion : UTCTimestamp; AttackName : ShortString; AttackType : ShortString; CorrelationId : ShortString; CorrelationSubId : ShortString; Event : ShortString; EventLogType : ShortString; EventMessage : LongString; EventScenarioRoleOfActor : ShortString; EventScenarioRoleOfInitiator : ShortString; EventSeverityCode : ShortString; EventSourceId : ShortString; EventSourceType : ShortString; GenericAction : ShortString; GenericCategory : ShortString; GenericDeviceType : ShortString; GenericExplanation : LongString; GenericGeolocationCodeActor : ShortString; GenericGeolocationCodeTarget : ShortString; GenericOrder : Integer64; GenericOutcome : ShortString; GenericOutcomeReason : ShortString; GenericPath : LongString; GenericPathPrior : LongString; GenericPurpose : ShortString; GenericRiskLevel : ShortString; GenericScore : Integer64; GenericSessionId : ShortString; GenericURI : LongString; NetworkHostnameActor : ShortString; NetworkHostnameInitiator : ShortString; NetworkHostnameIntermediary : ShortString; NetworkHostnameReporter : ShortString; NetworkHostnameTarget : ShortString; NetworkHostDomainActor : ShortString; NetworkHostDomainInitiator : ShortString; NetworkHostDomainIntermediary : ShortString; NetworkHostDomainReporter : ShortString; NetworkHostDomainTarget : ShortString; NetworkInterfaceActor : ShortString; NetworkInterfaceTarget : ShortString; NetworkIPAddressActor : ShortString; NetworkIPAddressInitiator : ShortString; NetworkIPAddressIntermediary : ShortString; NetworkIPAddressReporter : ShortString; NetworkIPAddressTarget : ShortString; NetworkIPBeforeNATActor : ShortString; NetworkIPBeforeNATTarget : ShortString; NetworkMACAddressActor : ShortString; NetworkMACAddressInitiator : ShortString; NetworkMACAddressIntermediary : ShortString; NetworkMACAddressReporter : ShortString; NetworkMACAddressTarget : ShortString; NetworkNetworkPrefixActor : ShortString; NetworkNetworkPrefixTarget : ShortString; NetworkPortActor : Integer; NetworkPortInitiator : Integer; NetworkPortIntermediary : Integer; NetworkPortReporter : Integer; NetworkPortTarget : Integer; NetworkPortBeforeNATActor : Integer; NetworkPortBeforeNATTarget : Integer; NetworkProtocol : ShortString; NetworkSessionId : ShortString; NetworkSubnetIdActor : UUID; NetworkSubnetIdInitiator : UUID; NetworkSubnetIdIntermediary : UUID; NetworkSubnetIdReporter : UUID; NetworkSubnetIdTarget : UUID; NetworkZoneActor : ShortString; NetworkZoneTarget : ShortString; ParameterDirection : ShortString; ParameterDirectionContext : ShortString; ParameterName : ShortString; ParameterNameContext : ShortString; ParameterDataType : ShortString; ParameterDataTypeContext : ShortString; ParameterType : ShortString; ParameterTypeContext : ShortString; ParameterValueNumber : Integer64; ParameterValueNumberContext : Integer64; ParameterValueNumberPriorValue : Integer64; ParameterValueString : LongString; ParameterValueStringContext : LongString; ParameterValueStringPriorValue : LongString; ParameterValueDouble : BinaryFloat; ParameterValueDoublePriorValue : BinaryFloat; Param eterValueTimestamp : UTCTimestamp; ParameterValueTimestampPriorValue : UTCTimestamp; PrivilegeIsGrantable : Boolean; PrivilegeName : ShortString; PrivilegeType : ShortString; PrivilegeGranteeName : ShortString; PrivilegeGranteeType : ShortString; ResourceContainerName : ShortString; ResourceContainerType : ShortString; ResourceContent : LongString; ResourceContentType : ShortString; ResourceCount : Integer64; ResourceName : ShortString; ResourceNamePrior : ShortString; ResourceRequestSize : Integer64; ResourceResponseSize : Integer64; ResourceSize : Integer64; ResourceType : ShortString; ResourceSumCriteria : ShortString; ResourceSumOverTime : BinaryFloat; ResourceUnitsOfMeasure : ShortString; ServiceAccessName : ShortString; ServiceFunctionName : ShortString; ServiceReferrer : ShortString; ServiceRequestLine : LongString; ServiceType : ShortString; ServiceVersion : ShortString; ServiceApplicationName : ShortString; ServiceExecutableName : ShortString; ServiceExecutableType : ShortString; ServiceInstanceName : ShortString; ServiceOutcome : ShortString; ServicePartId : ShortString; ServiceProcessId : ShortString; ServiceProgramName : ShortString; ServiceTransactionName : ShortString; ServiceUserAgent : ShortString; ServiceWorkflowName : ShortString; SystemIdActor : ShortString; SystemIdInitiator : ShortString; SystemIdIntermediary : ShortString; SystemIdReporter : ShortString; SystemIdTarget : ShortString; SystemTypeActor : ShortString; SystemTypeInitiator : ShortString; SystemTypeIntermediary : ShortString; SystemTypeReporter : ShortString; SystemTypeTarget : ShortString; TimeDuration : Integer64; TimestampOffind : UTCTimestamp; TimestampOfStart : UTCTimestamp; TriggerNameActing : ShortString; TriggerNameTargeted : ShortString; TriggerTypeActing : ShortString; TriggerTypeTargeted : ShortString; UserLogonMethod : ShortString; UsernameActing : ShortString; UsernameInitiating : ShortString; UsemameTargeted : ShortString; UsernameTargeting : ShortString; UsernameDomainNameActing : ShortString; UsernameDomainNameInitiating : ShortString; UsernameDomainNameTargeted : ShortString; UsernameDomainNameTargeting : ShortString; UsernameDomainTypeActing : ShortString; UsernameDomainTypeInitiating : ShortString; UsernameDomainTypeTargeted : ShortString; UsemameDomainTypeTargeting : ShortString; UserIdActing : UUID; UserIdInitiating : UUID; UserIdTargeted : UUID; UserIdTargeting : UUID; }.

Turning to FIG. 3, FIG. 3 is a block diagram illustrating additional detail of the dispatcher of the realtime ETD triggering framework, according to an implementation. Expanding on the explanation above, FIG. 3 illustrates that a “By Event” trigger manager 304 reads “By Event” registrations from the trigger persistency 104. Each registration, in addition to containing a PatternId value, contains a SemanticEventId. A corresponding field contains a SemanticEvent. Dispatcher 106 determines (for example, every 1 second) if, for these SemanticEventIds, any events containing the corresponding SemanticEvent arrived in the event persistency 108. If the determining is TRUE, then a list of such registrations is created by the dispatcher 106 to allocated ETD patterns associated with the registrations to individual threads 110.

Returning to FIG. 1, dispatcher 106 creates triggering threads 110 that run independently from dispatcher 110. After threads 110 finished processing their assigned ETD patterns, no return to dispatcher happens and threads end themselves. Once the dispatcher 106 creates threads and passes PatternIds to the threads 110 to begin execution of corresponding ETD patterns, the dispatcher 106's job completes and it is ready to read a next portion of events from event persistency 108. Usually, the dispatcher 106 waits a configured time (for example, 1 second) for the next reading. In some implementations, the amount of time waited can be manually determined, dynamically determined, and dynamically-adjustable based on execution of various components of the ETD triggering framework 100, etc.

The threads 110 are typically written in JAVASCRIPT and delegate execution of ETD patterns to the pattern execution framework 112 (for example, using a library-to-library in-process communication) from within the same thread 110. In typical implementations, the pattern execution framework 112 is a JAVASCRIPT library that is able to execute ETD patterns. If ETD pattern execution returns a findings (particularly an alert), then the pattern execution framework 112 calls dispatcher 106 and passes the PatternId of the ETD pattern whose execution resulted in the alert. The dispatcher 106 reads the triggering persistency 104 to determine if there is a registration for triggering “By Pattern” for the PatternId.

If an alert results from the execution of an ETD pattern, pattern execution framework 112 detects the alert and sends a PatternId of the executed ETD pattern that caused the alert to the dispatcher 106.

Turning again to FIG. 3, FIG. 3 illustrates a “By Pattern” trigger manager 306. The “By Pattern” trigger manager 306 receives from the pattern execution framework 112 a PatternId of an ETD pattern whose execution resulted in alert(s).

In typical implementations, the content of field “TechnicalLogEntryType” in the example event persistence 108 structure above is converted (for example, name to id) and compared with field “TriggerName” in the trigger persistency 104. This conversion is typically computationally very fast. Note that other methods are possible to determining whether additional ETD patterns are registered to be executed following an alert raised when executing an ETD pattern. To the extent other methods are consistent with this disclosure, they are also considered to be within the scope of this disclosure.

If a determination is made that there are additional registered ETD patterns in the trigger persistency 104 corresponding to the PatternId received by the “By Pattern” trigger manager 306, for each additional trigger registration. A distinct thread 110 is allocated by dispatcher 106 to execute each ETD pattern associated with the trigger registration. Each thread 110 delegates the execution of its associated ETD pattern to the pattern execution framework 112. This approach allows the definition of chains (workflows) of ETD pattern processing. Using this methodology, complex and expensive ETD patterns can be divided into a chain of simple ETD patterns [inventors—can you provide a simple example of this?]. This division can reduce complexity and allows a chain to be broken/terminated if one of the chained ETD patterns results in no findings. At some point in the execution of an ETD pattern chain, a fork (for example, calling several ETD patterns simultaneously to execute in parallel) can also be performed. This forking functionality permits faster execution and receipt of ETD pattern execution results.

Returning to FIG. 1, pattern execution framework 112 can also determine if an alert resulting from an executed ETD pattern was previously reported. Pattern execution framework 112 persists alerts along with additional information (attributes) identifying this alert in a separate persistency layer (an alert persistency) (not illustrated). If an alert matches to an alert in the alert persistency, then no additional actions are done. If the alert does not match to any alerts in the alert persistency, then the alert is considered as a new alert and the dispatcher 106 receives control information for further processing. Consistent with the explanation above, an alert is a SQL query result (a table) that is returned by a SQL query execution (a pattern execution on a technical layer). Alerts are usually persisted by the pattern execution framework 112 for long periods of time (for example, years) for purposes such as auditability, later proof of a found attack/threat, etc.

In typical implementations, there is a monitoring user interface (not illustrated) for alert monitoring and a user interface for displaying ETD pattern execution results (also not illustrated). These user interfaces read over persisted alerts and execution results and execute in separate processes from the triggering framework (see FIG. 3) and pattern execution framework 112.

FIGS. 4B and 4B illustrate a flowchart of an example method 400 (400 a & 400 b) for realtime ETD threat detection, according to an implementation. For clarity of presentation, the description that follows generally describes method 400 in the context of the other figures in this description. However, it will be understood that method 400 may be performed, for example, by any suitable system, environment, software, and hardware, or a combination of systems, environments, software, and hardware as appropriate. In some implementations, various steps of method 400 can be run in parallel, in combination, in loops, or in any order.

At 402, a saved maximum timestamp is read from the triggering persistency and assigned as FromTS. If a maximum timestamp value has not yet been saved, then the MAX timestamp of the logs in the events persistency is used instead as the FromTS value. This happens on the very first dispatcher job run after ETD installation. From 402, method 400 proceeds to 404.

At 404, a current maximum timestamp is read from the event persistency and assigned as ToTS. If there are no events in the event persistency, then the maximum timestamp of the events cannot be retrieved. In this case the further processing is skipped and the job loop starts from the beginning (after waiting of a configured repetition time, for example one second). This is likely to happen in an incomplete ETD installation or other anomalous system condition, when the dispatcher job is already running, but the event persistency is not yet receiving any logs data. From 404, method 400 proceeds to 406.

At 406, registered triggers of type “By Event” are read from the trigger persistency. From 406, method 400 proceeds to 408.

At 408, registered trigger content is matched with data from the event persistency associated with read events for the time range between FromTS and ToTS. From 408, method 408 proceeds to 410.

At 410, a determination is made as to whether read event data matches registered trigger content (by pattern) or one or more semantic value (by event) trigger registrations in the triggering persistency (in the registration list). If it is determined that a match has not occurred, method 400 proceeds to 412. Otherwise, if it is determined that a match has occurred, method 200 proceeds to 414.

At 412, the ToTS value is saved as FromTS in the trigger persistency. From 412, method 400 job loop proceeds back to 402.

At 414, a thread is created for each match and a PatternId is passed to each thread identifying an ETD pattern to execute. From 414, method 400 proceeds to 416.

At 416, two actions are taken: 1) at 412, the ToTS value is saved as FromTS in the trigger persistency and the method 400 job loop proceeds back to 402; and 2) method 400 proceeds to 418 in FIG. 4B.

At 418, the pattern execution framework is delegated the task of executing/processing an ETD pattern by each thread. From 418, method 400 proceeds to 420.

At 420, method 420, the pattern execution framework processes the ETD pattern.

The pattern execution framework notifies the thread when processing is complete so the thread can terminate. From 420, method 400 proceeds to 422.

At 422, the pattern execution framework determines if the execution of an ETD pattern resulted in an alert. From 422, method 400 proceeds to 424.

At 424, a determination is made as to whether an alert occurred from ETD pattern processing. If it is determined that an alert did not occur, method 400 proceeds to 426 where method 400 stops. Otherwise, if it is determined that an alert did occur, method 400 proceeds to 428.

At 428, the “By Pattern” trigger manager in the dispatcher is passed the PatternId of the ETD pattern that caused the alert. From 428, method 400 proceeds to 430.

At 430, the “By Pattern” trigger manager reads registered “By Pattern” triggers in the trigger persistency. From 430, method 400 proceeds to 432.

At 432, the “By Pattern” trigger manager attempts to match registered trigger content with the provided PatternId. From 432, method 400 proceeds to 434.

At 434, a determination is made as to whether a match exists between registered trigger content and the provided PatternId. If it is determined that a match does not exist, method 400 proceeds to 436 where method 400 stops. Otherwise, if it is determined that a match does exist, method 400 proceeds to 438.

At 438, a thread is created for each match and a PatternId is passed to each thread identifying an ETD pattern to execute. From 438, method 400 proceeds back to 418 to determine if an additional alert occurs from the execution of the ETD pattern.

FIG. 5 is a block diagram of an exemplary computer system 500 used to provide computational functionalities associated with described algorithms, methods, functions, processes, flows, and procedures as described in the instant disclosure, according to an implementation. The illustrated computer 502 is intended to encompass any computing device such as a server, desktop computer, laptop/notebook computer, wireless data port, smart phone, personal data assistant (PDA), tablet computing device, one or more processors within these devices, or any other suitable processing device, including both physical or virtual instances (or both) of the computing device. Additionally, the computer 502 may comprise a computer that includes an input device, such as a keypad, keyboard, touch screen, or other device that can accept user information, and an output device that conveys information associated with the operation of the computer 502, including digital data, visual, or audio information (or a combination of information), or a GUI.

The computer 502 can serve in a role as a client, network component, a server, a database or other persistency, or any other component (or a combination of roles) of a computer system for performing the subject matter described in the instant disclosure. The illustrated computer 502 is communicably coupled with a network 530. In some implementations, one or more components of the computer 502 may be configured to operate within environments, including cloud-computing-based, local, global, or other environment (or a combination of environments).

At a high level, the computer 502 is an electronic computing device operable to receive, transmit, process, store, or manage data and information associated with the described subject matter. According to some implementations, the computer 502 may also include or be communicably coupled with an application server, e-mail server, web server, caching server, streaming data server, business intelligence (BI) server, or other server (or a combination of servers).

The computer 502 can receive requests over network 530 from a client application (for example, executing on another computer 502) and responding to the received requests by processing the said requests in an appropriate software application. In addition, requests may also be sent to the computer 502 from internal users (for example, from a command console or by other appropriate access method), external or third-parties, other automated applications, as well as any other appropriate entities, individuals, systems, or computers.

Each of the components of the computer 502 can communicate using a system bus 503. In some implementations, any or all of the components of the computer 502, both hardware or software (or a combination of hardware and software), may interface with each other or the interface 504 (or a combination of both) over the system bus 503 using an application programming interface (API) 512 or a service layer 513 (or a combination of the API 512 and service layer 513). The API 512 may include specifications for routines, data structures, and object classes. The API 512 may be either computer-language independent or dependent and refer to a complete interface, a single function, or even a set of APIs. The service layer 513 provides software services to the computer 502 or other components (whether or not illustrated) that are communicably coupled to the computer 502. The functionality of the computer 502 may be accessible for all service consumers using this service layer. Software services, such as those provided by the service layer 513, provide reusable, defined business functionalities through a defined interface. For example, the interface may be software written in JAVA, C++, or other suitable language providing data in extensible markup language (XML) format or other suitable format. While illustrated as an integrated component of the computer 502, alternative implementations may illustrate the API 512 or the service layer 513 as stand-alone components in relation to other components of the computer 502 or other components (whether or not illustrated) that are communicably coupled to the computer 502. Moreover, any or all parts of the API 512 or the service layer 513 may be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of this disclosure.

The computer 502 includes an interface 504. Although illustrated as a single interface 504 in FIG. 5, two or more interfaces 504 may be used according to particular needs, desires, or particular implementations of the computer 502. The interface 504 is used by the computer 502 for communicating with other systems in a distributed environment that are connected to the network 530 (whether illustrated or not). Generally, the interface 504 comprises logic encoded in software or hardware (or a combination of software and hardware) and operable to communicate with the network 530. More specifically, the interface 504 may comprise software supporting one or more communication protocols associated with communications such that the network 530 or interface's hardware is operable to communicate physical signals within and outside of the illustrated computer 502.

The computer 502 includes a processor 505. Although illustrated as a single processor 505 in FIG. 5, two or more processors may be used according to particular needs, desires, or particular implementations of the computer 502. Generally, the processor 505 executes instructions and manipulates data to perform the operations of the computer 502 and any algorithms, methods, functions, processes, flows, and procedures as described in the instant disclosure.

The computer 502 also includes a database 506 that can hold data for the computer 502 or other components (or a combination of both) that can be connected to the network 530 (whether illustrated or not). For example, database 506 can be an in-memory, conventional, or other type of database storing data consistent with this disclosure. In some implementations, database 506 can be a combination of two or more different database types (for example, a hybrid in-memory and conventional database) according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. Although illustrated as a single database 506 in FIG. 5, two or more databases (of the same or combination of types) can be used according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. While database 506 is illustrated as an integral component of the computer 502, in alternative implementations, database 506 can be external to the computer 502.

The computer 502 also includes a memory 507 that can hold data for the computer 502 or other components (or a combination of both) that can be connected to the network 530 (whether illustrated or not). For example, memory 507 can be random access memory (RAM), read-only memory (ROM), optical, magnetic, and the like storing data consistent with this disclosure. In some implementations, memory 507 can be a combination of two or more different types of memory (for example, a combination of RAM and magnetic storage) according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. Although illustrated as a single memory 507 in FIG. 5, two or more memories 507 (of the same or combination of types) can be used according to particular needs, desires, or particular implementations of the computer 502 and the described functionality. While memory 507 is illustrated as an integral component of the computer 502, in alternative implementations, memory 507 can be external to the computer 502.

The application 508 is an algorithmic software engine providing functionality according to particular needs, desires, or particular implementations of the computer 502, particularly with respect to functionality described in this disclosure. For example, application 508 can serve as one or more components, modules, applications, etc. Further, although illustrated as a single application 508, the application 508 may be implemented as multiple applications 507 on the computer 502. In addition, although illustrated as integral to the computer 502, in alternative implementations, the application 508 can be external to the computer 502.

There may be any number of computers 502 associated with, or external to, a computer system containing computer 502, each computer 502 communicating over network 530. Further, the term “client,” “user,” and other appropriate terminology may be used interchangeably as appropriate without departing from the scope of this disclosure. Moreover, this disclosure contemplates that many users may use one computer 502, or that one user may use multiple computers 502.

Described implementations of the subject matter can include one or more features, alone or in combination.

For example, in a first implementation, a computer-implemented method, comprising: generating a trigger registration for a selected triggering type; storing the generated trigger registration in a triggering persistency; analyzing a received event from an event persistency; comparing data associated with the analyzed event with the triggering persistency; and based on the comparison, processing, using a pattern execution framework, an enterprise threat detection (ETD) pattern to perform actions responsive to the received event.

The foregoing and other described implementations can each optionally include one or more of the following features:

A first feature, combinable with any of the following features, wherein the triggering type includes one of the group consisting of by event and by pattern.

A second feature, combinable with any of the previous or following features, wherein the trigger registration is stored in a triggering persistency registration list.

A third feature, combinable with any of the previous or following features, comprising determining that the data associated with the analyzed event matches registered content or one or more semantic value trigger registrations in the triggering persistency registration list.

A fourth feature, combinable with any of the previous or following features, comprising: instantiating a processing thread to process the ETD pattern; and delegating the processing of the ETD pattern from the processing thread to the pattern execution framework.

A fifth feature, combinable with any of the previous or following features, comprising determining that execution of the ETD pattern generates an additional event.

A sixth feature, combinable with any of the previous or following features, comprising determining whether a triggering registration for the additional event exists in the triggering persistency.

In a second implementation, a non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising: generating a trigger registration for a selected triggering type; storing the generated trigger registration in a triggering persistency; analyzing a received event from an event persistency; comparing data associated with the analyzed event with the triggering persistency; and based on the comparison, processing, using a pattern execution framework, an enterprise threat detection (ETD) pattern to perform actions responsive to the received event.

The foregoing and other described implementations can each optionally include one or more of the following features:

A first feature, combinable with any of the following features, wherein the triggering type includes one of the group consisting of by event and by pattern.

A second feature, combinable with any of the previous or following features, wherein the trigger registration is stored in a triggering persistency registration list.

A third feature, combinable with any of the previous or following features, comprising one or more instructions to determine that the data associated with the analyzed event matches registered content or one or more semantic value trigger registrations in the triggering persistency registration list.

A fourth feature, combinable with any of the previous or following features, comprising one or more instructions to: instantiate a processing thread to process the ETD pattern; and delegate the processing of the ETD pattern from the processing thread to the pattern execution framework.

A fifth feature, combinable with any of the previous or following features, comprising one or more instructions to determine that execution of the ETD pattern generates an additional event.

A sixth feature, combinable with any of the previous or following features, comprising one or more instructions to determine whether a triggering registration for the additional event exists in the triggering persistency.

In a third implementation, a computer-implemented system, comprising: a hardware processor interoperably coupled with a computer memory and configured to perform operations comprising: generating a trigger registration for a selected triggering type; storing the generated trigger registration in a triggering persistency; analyzing a received event from an event persistency; comparing data associated with the analyzed event with the triggering persistency; and based on the comparison, processing, using a pattern execution framework, an enterprise threat detection (ETD) pattern to perform actions responsive to the received event.

The foregoing and other described implementations can each optionally include one or more of the following features:

A first feature, combinable with any of the following features, wherein the triggering type includes one of the group consisting of by event and by pattern.

A second feature, combinable with any of the previous or following features, wherein the trigger registration is stored in a triggering persistency registration list.

A third feature, combinable with any of the previous or following features, configured to determine that the data associated with the analyzed event matches registered content or one or more semantic value trigger registrations in the triggering persistency registration list.

A fourth feature, combinable with any of the previous or following features, configured to: instantiate a processing thread to process the ETD pattern; and delegate the processing of the ETD pattern from the processing thread to the pattern execution framework.

A fifth feature, combinable with any of the previous or following features, configured to determine that execution of the ETD pattern generates an additional event.

A sixth feature, combinable with any of the previous or following features, configured to determine whether a triggering registration for the additional event exists in the triggering persistency.

Implementations of the subject matter and the functional operations described in this specification can be implemented in digital electronic circuitry, in tangibly embodied computer software or firmware, in computer hardware, including the structures disclosed in this specification and their structural equivalents, or in combinations of one or more of them. Implementations of the subject matter described in this specification can be implemented as one or more computer programs, that is, one or more modules of computer program instructions encoded on a tangible, non-transitory, computer-readable computer-storage medium for execution by, or to control the operation of, data processing apparatus. Alternatively or in addition, the program instructions can be encoded on an artificially generated propagated signal, for example, a machine-generated electrical, optical, or electromagnetic signal that is generated to encode information for transmission to suitable receiver apparatus for execution by a data processing apparatus. The computer-storage medium can be a machine-readable storage device, a machine-readable storage substrate, a random or serial access memory device, or a combination of computer-storage mediums.

The terms “data processing apparatus,” “computer,” or “electronic computer device” (or equivalent as understood by one of ordinary skill in the art) refer to data processing hardware and encompass all kinds of apparatus, devices, and machines for processing data, including by way of example, a programmable processor, a computer, or multiple processors or computers. The apparatus can also be or further include special purpose logic circuitry, for example, a central processing unit (CPU), an FPGA (field programmable gate array), or an ASIC (application-specific integrated circuit). In some implementations, the data processing apparatus or special purpose logic circuitry (or a combination of the data processing apparatus or special purpose logic circuitry) may be hardware- or software-based (or a combination of both hardware- and software-based). The apparatus can optionally include code that creates an execution environment for computer programs, for example, code that constitutes processor firmware, a protocol stack, a database management system, an operating system, or a combination of execution environments. The present disclosure contemplates the use of data processing apparatuses with or without conventional operating systems, for example LINUX, UNIX, WINDOWS, MAC OS, ANDROID, IOS, or any other suitable conventional operating system.

A computer program, which may also be referred to or described as a program, software, a software application, a module, a software module, a script, or code can be written in any form of programming language, including compiled or interpreted languages, or declarative or procedural languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program may, but need not, correspond to a file in a file system. A program can be stored in a portion of a file that holds other programs or data, for example, one or more scripts stored in a markup language document, in a single file dedicated to the program in question, or in multiple coordinated files, for example, files that store one or more modules, sub-programs, or portions of code. A computer program can be deployed to be executed on one computer or on multiple computers that are located at one site or distributed across multiple sites and interconnected by a communication network. While portions of the programs illustrated in the various figures are shown as individual modules that implement the various features and functionality through various objects, methods, or other processes, the programs may instead include a number of sub-modules, third-party services, components, libraries, and such, as appropriate. Conversely, the features and functionality of various components can be combined into single components as appropriate.

The processes and logic flows described in this specification can be performed by one or more programmable computers executing one or more computer programs to perform functions by operating on input data and generating output. The processes and logic flows can also be performed by, and apparatus can also be implemented as, special purpose logic circuitry, for example, a CPU, an FPGA, or an ASIC.

Computers suitable for the execution of a computer program can be based on general or special purpose microprocessors, both, or any other kind of CPU. Generally, a CPU will receive instructions and data from a read-only memory (ROM) or a random access memory (RAM), or both. The essential elements of a computer are a CPU, for performing or executing instructions, and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to, receive data from or transfer data to, or both, one or more mass storage devices for storing data, for example, magnetic, magneto-optical disks, or optical disks. However, a computer need not have such devices. Moreover, a computer can be embedded in another device, for example, a mobile telephone, a personal digital assistant (PDA), a mobile audio or video player, a game console, a global positioning system (GPS) receiver, or a portable storage device, for example, a universal serial bus (USB) flash drive, to name just a few.

Computer-readable media (transitory or non-transitory, as appropriate) suitable for storing computer program instructions and data include all forms of non-volatile memory, media and memory devices, including by way of example semiconductor memory devices, for example, erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), and flash memory devices; magnetic disks, for example, internal hard disks or removable disks; magneto-optical disks; and CD-ROM, DVD+/−R, DVD-RAM, and DVD-ROM disks. The memory may store various objects or data, including caches, classes, frameworks, applications, backup data, jobs, web pages, web page templates, database tables, repositories storing dynamic information, and any other appropriate information including any parameters, variables, algorithms, instructions, rules, constraints, or references thereto. Additionally, the memory may include any other appropriate data, such as logs, policies, security or access data, reporting files, as well as others. The processor and the memory can be supplemented by, or incorporated in, special purpose logic circuitry.

To provide for interaction with a user, implementations of the subject matter described in this specification can be implemented on a computer having a display device, for example, a CRT (cathode ray tube), LCD (liquid crystal display), LED (Light Emitting Diode), or plasma monitor, for displaying information to the user and a keyboard and a pointing device, for example, a mouse, trackball, or trackpad by which the user can provide input to the computer. Input may also be provided to the computer using a touchscreen, such as a tablet computer surface with pressure sensitivity, a multi-touch screen using capacitive or electric sensing, or other type of touchscreen. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, for example, visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input. In addition, a computer can interact with a user by sending documents to and receiving documents from a device that is used by the user; for example, by sending web pages to a web browser on a user's client device in response to requests received from the web browser.

The term “graphical user interface,” or “GUI,” may be used in the singular or the plural to describe one or more graphical user interfaces and each of the displays of a particular graphical user interface. Therefore, a GUI may represent any graphical user interface, including but not limited to, a web browser, a touch screen, or a command line interface (CLI) that processes information and efficiently presents the information results to the user. In general, a GUI may include a plurality of user interface (UI) elements, some or all associated with a web browser, such as interactive fields, pull-down lists, and buttons operable by the business suite user. These and other UI elements may be related to or represent the functions of the web browser.

Implementations of the subject matter described in this specification can be implemented in a computing system that includes a back-end component, for example, as a data server, or that includes a middleware component, for example, an application server, or that includes a front-end component, for example, a client computer having a graphical user interface or a Web browser through which a user can interact with an implementation of the subject matter described in this specification, or any combination of one or more such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of wireline or wireless digital data communication (or a combination of data communication), for example, a communication network. Examples of communication networks include a local area network (LAN), a radio access network (RAN), a metropolitan area network (MAN), a wide area network (WAN), Worldwide Interoperability for Microwave Access (WIMAX), a wireless local area network (WLAN) using, for example, 802.11 a/b/g/n or 802.20 (or a combination of 802.11x and 802.20 or other protocols consistent with this disclosure), all or a portion of the Internet, or any other communication system or systems at one or more locations (or a combination of communication networks). The network may communicate with, for example, Internet Protocol (IP) packets, Frame Relay frames, Asynchronous Transfer Mode (ATM) cells, voice, video, data, or other suitable information (or a combination of communication types) between network addresses.

The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.

In some implementations, any or all of the components of the computing system, both hardware or software (or a combination of hardware and software), may interface with each other or the interface using an application programming interface (API) or a service layer (or a combination of API and service layer). The API may include specifications for routines, data structures, and object classes. The API may be either computer language independent or dependent and refer to a complete interface, a single function, or even a set of APIs. The service layer provides software services to the computing system. The functionality of the various components of the computing system may be accessible for all service consumers using this service layer. Software services provide reusable, defined business functionalities through a defined interface. For example, the interface may be software written in JAVA, C++, or other suitable language providing data in extensible markup language (XML) format or other suitable format. The API or service layer (or a combination of the API and the service layer) may be an integral or a stand-alone component in relation to other components of the computing system. Moreover, any or all parts of the service layer may be implemented as child or sub-modules of another software module, enterprise application, or hardware module without departing from the scope of this disclosure.

While this specification contains many specific implementation details, these should not be construed as limitations on the scope of any invention or on the scope of what may be claimed, but rather as descriptions of features that may be specific to particular implementations of particular inventions. Certain features that are described in this specification in the context of separate implementations can also be implemented, in combination, in a single implementation. Conversely, various features that are described in the context of a single implementation can also be implemented in multiple implementations, separately, or in any suitable sub-combination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can, in some cases, be excised from the combination, and the claimed combination may be directed to a sub-combination or variation of a sub-combination.

Particular implementations of the subject matter have been described. Other implementations, alterations, and permutations of the described implementations are within the scope of the following claims as will be apparent to those skilled in the art. While operations are depicted in the drawings or claims in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed (some operations may be considered optional), to achieve desirable results. In certain circumstances, multitasking or parallel processing (or a combination of multitasking and parallel processing) may be advantageous and performed as deemed appropriate.

Moreover, the separation or integration of various system modules and components in the implementations described above should not be understood as requiring such separation or integration in all implementations, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

Accordingly, the above description of example implementations does not define or constrain this disclosure. Other changes, substitutions, and alterations are also possible without departing from the spirit and scope of this disclosure.

Furthermore, any claimed implementation below is considered to be applicable to at least a computer-implemented method; a non-transitory, computer-readable medium storing computer-readable instructions to perform the computer-implemented method; and a computer system comprising a computer memory interoperably coupled with a hardware processor configured to perform the computer-implemented method or the instructions stored on the non-transitory, computer-readable medium. 

1.-20. (canceled)
 21. A computer-implemented method, comprising: generating a trigger registration for a selected triggering type; storing the generated trigger registration in a triggering persistency; analyzing a received event from an event persistency; comparing forensic data associated with the analyzed event with the triggering persistency; and based on the comparison, processing, using a pattern execution framework, an enterprise threat detection (ETD) pattern to provide for display in realtime an alert associated with the ETD pattern.
 22. The computer-implemented method of claim 21, wherein the triggering type includes one of the group consisting of by event and by pattern.
 23. The computer-implemented method of claim 21, wherein the trigger registration is stored in a triggering persistency registration list.
 24. The computer-implemented method of claim 23, comprising determining that the data associated with the analyzed event matches registered content or one or more semantic value trigger registrations in the triggering persistency registration list.
 25. The computer-implemented method of claim 21, comprising: instantiating a processing thread to process the ETD pattern; and delegating the processing of the ETD pattern from the processing thread to the pattern execution framework.
 26. The computer-implemented method of claim 21, comprising determining that execution of the ETD pattern generates an additional event.
 27. The computer-implemented method of claim 26, comprising determining whether a triggering registration for the additional event exists in the triggering persistency.
 28. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising: generating a trigger registration for a selected triggering type; storing the generated trigger registration in a triggering persistency; analyzing a received event from an event persistency; comparing forensic data associated with the analyzed event with the triggering persistency; and based on the comparison, processing, using a pattern execution framework, an enterprise threat detection (ETD) pattern to provide for display in realtime an alert associated with the ETD pattern.
 29. The non-transitory, computer-readable medium of claim 28, wherein the triggering type includes one of the group consisting of by event and by pattern.
 30. The non-transitory, computer-readable medium of claim 28, wherein the trigger registration is stored in a triggering persistency registration list.
 31. The non-transitory, computer-readable medium of claim 30, comprising one or more instructions to determine that the data associated with the analyzed event matches registered content or one or more semantic value trigger registrations in the triggering persistency registration list.
 32. The non-transitory, computer-readable medium of claim 28, comprising one or more instructions to: instantiate a processing thread to process the ETD pattern; and delegate the processing of the ETD pattern from the processing thread to the pattern execution framework.
 33. The non-transitory, computer-readable medium of claim 28, comprising one or more instructions to determine that execution of the ETD pattern generates an additional event.
 34. The non-transitory, computer-readable medium of claim 33, comprising one or more instructions to determine whether a triggering registration for the additional event exists in the triggering persistency.
 35. A computer-implemented system, comprising: a hardware processor interoperably coupled with a computer memory and configured to perform operations comprising: generating a trigger registration for a selected triggering type; storing the generated trigger registration in a triggering persistency; analyzing a received event from an event persistency; comparing forensic data associated with the analyzed event with the triggering persistency; and based on the comparison, processing, using a pattern execution framework, an enterprise threat detection (ETD) pattern to provide for display in realtime an alert associated with the ETD pattern.
 36. The computer-implemented system of claim 35, wherein the triggering type includes one of the group consisting of by event and by pattern.
 37. The computer-implemented system of claim 35, wherein the trigger registration is stored in a triggering persistency registration list.
 38. The computer-implemented system of claim 37, configured to determine that the data associated with the analyzed event matches registered content or one or more semantic value trigger registrations in the triggering persistency registration list.
 39. The computer-implemented system of claim 35, configured to: instantiate a processing thread to process the ETD pattern; and delegate the processing of the ETD pattern from the processing thread to the pattern execution framework.
 40. The computer-implemented system of claim 35, configured to: determine that execution of the ETD pattern generates an additional event; and determine whether a triggering registration for the additional event exists in the triggering persistency. 